Broadcast interactive television system

ABSTRACT

A system that incorporates teachings of the present disclosure may include, for example, a system for delivering broadcast channels by way of edge routers using multicast virtual private networks, sharing a same multicast state for the broadcast channels and sharing a same multicast delivery tree for the broadcast channels. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 13/613,126, filed Sep. 13, 2012, which is acontinuation of U.S. patent application Ser. No. 12/252,178 filed Oct.15, 2008, which are incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to interactive television (iTV)and more specifically to a broadcast iTV system.

BACKGROUND

To efficiently deliver broadcast iTV in a network of users, InternetProtocol (IP) multicast can be used. Multicast provides substantiallybetter bandwidth efficiencies over unicast delivery. For nationalchannels the iTV streams can be sent to local markets, independent ofwhether there are currently viewers in each local market for aparticular channel. This is done to improve channel change time latency.To accomplish this, static joins can be created on every edge deliveryrouter in the network across all local markets. Hundreds of channelshave been made available by iTV service providers and additionalchannels numbering in the thousands are expected in the near future. Theincrease in channels is not just due to new content, but also due tovariations for given content that can include channels for both standarddefinition resolution as well as high definition resolution. “Picture inPicture” resolution can be yet another “channel” stream. Multiple cameraangles for sporting events can also add channel streams.

As more channels are added to the iTV network, the state informationgrows. When nodes are added to the iTV network or maintenance isperformed on new nodes or links or when there are node or link failures,the time to reroute the multicast traffic depends on an amount ofmulticast routing states present in the network. Furthermore,pre-positioning multicast states in every local market edge router canrequire configuring static multicast joins in every one of the localmarket edge routers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-4 depict illustrative embodiments of communication systems thatprovide media services;

FIG. 5 depicts an illustrative embodiment of a portal interacting withat least one among the communication systems of FIGS. 1-4;

FIG. 6 depicts an illustrative embodiment of a communication deviceutilized in the communication systems of FIGS. 1-4;

FIG. 7 depicts an illustrative embodiment of a method operating inportions of the communication systems of FIGS. 1-4; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methodologiesdiscussed herein.

DETAILED DESCRIPTION

One embodiment of the present disclosure entails using nationalmulticast VPNs to deliver national broadcast channels by way of IPTVedge routers using a multi-protocol label switching (MPLS) protocol andsharing a same multicast state and a same multicast delivery tree forthe national broadcast channels.

Another embodiment of the present disclosure entails a computer-readablestorage medium that includes computer instructions for deliveringbroadcast channels by way of IPTV edge routers using multicast VPNs andapplying an MPLS protocol to the multicast VPNs to share a samemulticast state for the broadcast channels.

Yet another embodiment of the present disclosure entails a system havinga controller to deliver broadcast channels by way of interactive TV(iTV) edge routers using multicast VPNs, share a same multicast statefor the broadcast channels and share a same multicast delivery tree forthe broadcast channels.

Yet another embodiment of the present disclosure entails a networkarchitecture having a plurality of multicast VPNs used to deliverbroadcast channels by way of iTV edge routers and a controller adaptedto cause the iTV edge routers to share a same multicast state for thebroadcast channels and to share a same multicast delivery tree for thebroadcast channels.

FIG. 1 depicts an illustrative embodiment of a first communicationsystem 100 for delivering media content. The communication system 100can represent an Internet Protocol Television (IPTV) broadcast mediasystem. In a typical IPTV infrastructure, there is a super head-endoffice (SHO) with at least one super headend office server (SHS) whichreceives national media programs from satellite and/or media serversfrom service providers of multimedia broadcast channels. In the presentcontext, media programs can represent audio content, moving imagecontent such as videos, still image content, and/or combinationsthereof. The SHS server forwards IP packets associated with the mediacontent to video head-end servers (VHS) via a network of aggregationpoints such as video head-end offices (VHO) according to a commonmulticast communication method.

The VHS then distributes multimedia broadcast programs via an accessnetwork to commercial and/or residential buildings 102 housing a gateway104 (such as a residential gateway or RG). The access network canrepresent a bank of digital subscriber line access multiplexers (DSLAMs)located in a central office or a service area interface that providebroadband services over optical links or copper twisted pairs tobuildings 102. The gateway 104 distributes broadcast signals to mediaprocessors 106 such as Set-Top Boxes (STBs) which in turn presentbroadcast selections to media devices 108 such as computers ortelevision sets managed in some instances by a media controller 107(such as an infrared or RF remote control). Unicast traffic can also beexchanged between the media processors 106 and subsystems of the IPTVmedia system for services such as video-on-demand (VoD). It will beappreciated by one of ordinary skill in the art that the media devices108 and/or portable communication devices 116 shown in FIG. 1 can be anintegral part of the media processor 106 and can be communicativelycoupled to the gateway 104. In this particular embodiment, an integraldevice such as described can receive, respond, process and presentmulticast or unicast media content.

The IPTV media system can be coupled to one or more computing devices130 a portion of which can operate as a web server for providing portalservices over an Internet Service Provider (ISP) network 132 to fixedline media devices 108 or portable communication devices 116 by way of awireless access point 117 providing Wireless Fidelity or WiFi services,or cellular communication services (such as GSM, CDMA, UMTS, WiMAX,etc.).

A satellite broadcast television system can be used in place of the IPTVmedia system. In this embodiment, signals transmitted by a satellite 115can be intercepted by a satellite dish receiver 131 coupled to building102 which conveys media signals to the media processors 106. The mediareceivers 106 can be equipped with a broadband port to the ISP network132. Although not shown, the communication system 100 can also becombined or replaced with analog or digital broadcast distributionssystems such as cable TV systems.

FIG. 2 depicts an illustrative embodiment of a second communicationsystem 200 for delivering media content. Communication system 200 can beoverlaid or operably coupled with communication system 100 as anotherrepresentative embodiment of said communication system. The system 200includes a distribution switch/router system 228 at a central office218. The distribution switch/router system 228 receives video data via amulticast television stream 230 from a second distribution switch/router234 at an intermediate office 220. The multicast television stream 230includes Internet Protocol (IP) data packets addressed to a multicast IPaddress associated with a television channel. The distributionswitch/router system 228 can cache data associated with each televisionchannel received from the intermediate office 220.

The distribution switch/router system 228 also receives unicast datatraffic from the intermediate office 220 via a unicast traffic stream232. The unicast traffic stream 232 includes data packets related todevices located at a particular residence, such as the residence 202.For example, the unicast traffic stream 232 can include data trafficrelated to a digital subscriber line, a telephone line, another dataconnection, or any combination thereof. To illustrate, the unicasttraffic stream 232 can communicate data packets to and from a telephone212 associated with a subscriber at the residence 202. The telephone 212can be a Voice over Internet Protocol (VoIP) telephone. To furtherillustrate, the unicast traffic stream 232 can communicate data packetsto and from a personal computer 210 at the residence 202 via one or moredata routers 208. In an additional illustration, the unicast trafficstream 232 can communicate data packets to and from a set-top boxdevice, such as the set-top box devices 204, 206. The unicast trafficstream 232 can communicate data packets to and from the devices locatedat the residence 202 via one or more residential gateways 214 associatedwith the residence 202.

The distribution switch/router system 228 can send data to one or moreaccess switch/router systems 226. The access switch/router system 226can include or be included within a service area interface 216. In aparticular embodiment, the access switch/router system 226 can include aDSLAM. The access switch/router system 226 can receive data from thedistribution switch/router system 228 via a broadcast television (BTV)stream 222 and a plurality of unicast subscriber traffic streams 224.The BTV stream 222 can be used to communicate video data packetsassociated with a multicast stream.

For example, the BTV stream 222 can include a multicast virtual localarea network (VLAN) connection between the distribution switch/routersystem 228 and the access switch/router system 226. Each of theplurality of subscriber traffic streams 224 can be used to communicatesubscriber specific data packets. For example, the first subscribertraffic stream can communicate data related to a first subscriber, andthe nth subscriber traffic stream can communicate data related to an nthsubscriber. Each subscriber to the system 200 can be associated with arespective subscriber traffic stream 224. The subscriber traffic stream224 can include a subscriber VLAN connection between the distributionswitch/router system 228 and the access switch/router system 226 that isassociated with a particular set-top box device 204, 206, a particularresidence 202, a particular residential gateway 214, another deviceassociated with a subscriber, or any combination thereof.

In an illustrative embodiment, a set-top box device, such as the set-topbox device 204, receives a channel change command from an input device,such as a remoter control device. The channel change command canindicate selection of an IPTV channel. After receiving the channelchange command, the set-top box device 204 generates channel selectiondata that indicates the selection of the IPTV channel. The set-top boxdevice 204 can send the channel selection data to the accessswitch/router system 226 via the residential gateway 214. The channelselection data can include an Internet Group Management Protocol (IGMP)Join request. In an illustrative embodiment, the access switch/routersystem 226 can identify whether it is joined to a multicast groupassociated with the requested channel based on information in the IGMPJoin request.

If the access switch/router system 226 is not joined to the multicastgroup associated with the requested channel, the access switch/routersystem 226 can generate a multicast stream request. The multicast streamrequest can be generated by modifying the received channel selectiondata. In an illustrative embodiment, the access switch/router system 226can modify an IGMP Join request to produce a proxy IGMP Join request.The access switch/router system 226 can send the multicast streamrequest to the distribution switch/router system 228 via the BTV stream222. In response to receiving the multicast stream request, thedistribution switch/router system 228 can send a stream associated withthe requested channel to the access switch/router system 226 via the BTVstream 222.

FIG. 3 depicts an illustrative embodiment of a third communicationsystem 300 for delivering media content. Communication system 300 can beoverlaid or operably coupled with communication systems 100-200 asanother representative embodiment of said communication systems. Asshown, the system 300 can include a client facing tier 302, anapplication tier 304, an acquisition tier 306, and an operations andmanagement tier 308. Each tier 302, 304, 306, 308 is coupled to aprivate network 310, such as a network of common packet-switched routersand/or switches; to a public network 312, such as the Internet; or toboth the private network 310 and the public network 312. For example,the client-facing tier 302 can be coupled to the private network 310.Further, the application tier 304 can be coupled to the private network310 and to the public network 312. The acquisition tier 306 can also becoupled to the private network 310 and to the public network 312.Additionally, the operations and management tier 308 can be coupled tothe public network 312.

As illustrated in FIG. 3, the various tiers 302, 304, 306, 308communicate with each other via the private network 310 and the publicnetwork 312. For instance, the client-facing tier 302 can communicatewith the application tier 304 and the acquisition tier 306 via theprivate network 310. The application tier 304 can communicate with theacquisition tier 306 via the private network 310. Further, theapplication tier 304 can communicate with the acquisition tier 306 andthe operations and management tier 308 via the public network 312.Moreover, the acquisition tier 306 can communicate with the operationsand management tier 308 via the public network 312. In a particularembodiment, elements of the application tier 304, including, but notlimited to, a client gateway 350, can communicate directly with theclient-facing tier 302.

The client-facing tier 302 can communicate with user equipment via anaccess network 366, such as an IPTV access network. In an illustrativeembodiment, customer premises equipment (CPE) 314, 322 can be coupled toa local switch, router, or other device of the access network 366. Theclient-facing tier 302 can communicate with a first representativeset-top box device 316 via the first CPE 314 and with a secondrepresentative set-top box device 324 via the second CPE 322. In aparticular embodiment, the first representative set-top box device 316and the first CPE 314 can be located at a first customer premise, andthe second representative set-top box device 324 and the second CPE 322can be located at a second customer premise.

In another particular embodiment, the first representative set-top boxdevice 316 and the second representative set-top box device 324 can belocated at a single customer premise, both coupled to one of the CPE314, 322. The CPE 314, 322 can include routers, local area networkdevices, modems, such as digital subscriber line (DSL) modems, any othersuitable devices for facilitating communication between a set-top boxdevice and the access network 366, or any combination thereof.

In an illustrative embodiment, the client-facing tier 302 can be coupledto the CPE 314, 322 via fiber optic cables. In another illustrativeembodiment, the CPE 314, 322 can include DSL modems that are coupled toone or more network nodes via twisted pairs, and the client-facing tier302 can be coupled to the network nodes via fiber-optic cables. Eachset-top box device 316, 324 can process data received via the accessnetwork 366, via a common IPTV software platform.

The first set-top box device 316 can be coupled to a first externaldisplay device, such as a first television monitor 318, and the secondset-top box device 324 can be coupled to a second external displaydevice, such as a second television monitor 326. Moreover, the firstset-top box device 316 can communicate with a first remote control 320,and the second set-top box device 324 can communicate with a secondremote control 328. The set-top box devices 316, 324 can include IPTVset-top box devices; video gaming devices or consoles that are adaptedto receive IPTV content; personal computers or other computing devicesthat are adapted to emulate set-top box device functionalities; anyother device adapted to receive IPTV content and transmit data to anIPTV system via an access network; or any combination thereof.

In an illustrative, non-limiting embodiment, each set-top box device316, 324 can receive data, video, or any combination thereof, from theclient-facing tier 302 via the access network 366 and render or displaythe data, video, or any combination thereof, at the display device 318,326 to which it is coupled. In an illustrative embodiment, the set-topbox devices 316, 324 can include tuners that receive and decodetelevision programming signals or packet streams for transmission to thedisplay devices 318, 326. Further, the set-top box devices 316, 324 caneach include a STB processor 370 and a STB memory device 372 that isaccessible to the STB processor 370. In one embodiment, a computerprogram, such as the STB computer program 374, can be embedded withinthe STB memory device 372.

In an illustrative embodiment, the client-facing tier 302 can include aclient-facing tier (CFT) switch 330 that manages communication betweenthe client-facing tier 302 and the access network 366 and between theclient-facing tier 302 and the private network 310. As illustrated, theCFT switch 330 is coupled to one or more distribution servers, such asDistribution-servers (D-servers) 332, that store, format, encode,replicate, or otherwise manipulate or prepare video content forcommunication from the client-facing tier 302 to the set-top box devices316, 324. The CFT switch 330 can also be coupled to a terminal server334 that provides terminal devices with a point of connection to theIPTV system 300 via the client-facing tier 302.

In a particular embodiment, the CFT switch 330 can be coupled to a VoDserver 336 that stores or provides VoD content imported by the IPTVsystem 300. Further, the CFT switch 330 is coupled to one or more videoservers 380 that receive video content and transmit the content to theset-top boxes 316, 324 via the access network 366. The client-facingtier 302 may include a CPE management server 382 that managescommunications to and from the CPE 314 and the CPE 322. For example, theCPE management server 382 may collect performance data associated withthe set-top box devices 316, 324 from the CPE 314 or the CPE 322 andforward the collected performance data to a server associated with theoperations and management tier 308.

In an illustrative embodiment, the client-facing tier 302 cancommunicate with a large number of set-top boxes, such as therepresentative set-top boxes 316, 324, over a wide geographic area, suchas a metropolitan area, a viewing area, a statewide area, a regionalarea, a nationwide area or any other suitable geographic area, marketarea, or subscriber or customer group that can be supported bynetworking the client-facing tier 302 to numerous set-top box devices.In a particular embodiment, the CFT switch 330, or any portion thereof,can include a multicast router or switch that communicates with multipleset-top box devices via a multicast-enabled network.

As illustrated in FIG. 3, the application tier 304 can communicate withboth the private network 310 and the public network 312. The applicationtier 304 can include a first application tier (APP) switch 338 and asecond APP switch 340. In a particular embodiment, the first APP switch338 can be coupled to the second APP switch 340. The first APP switch338 can be coupled to an application server 342 and to an OSS/BSSgateway 344. In a particular embodiment, the application server 342 canprovide applications to the set-top box devices 316, 324 via the accessnetwork 366, which enable the set-top box devices 316, 324 to providefunctions, such as interactive program guides, video gaming, display,messaging, processing of VoD material and other IPTV content, etc. In anillustrative embodiment, the application server 342 can provide locationinformation to the set-top box devices 316, 324. In a particularembodiment, the OSS/BSS gateway 344 includes operation systems andsupport (OSS) data, as well as billing systems and support (BSS) data.In one embodiment, the OSS/BSS gateway 344 can provide or restrictaccess to an OSS/BSS server 364 that stores operations and billingsystems data.

The second APP switch 340 can be coupled to a domain controller 346 thatprovides Internet access, for example, to users at their computers 368via the public network 312. For example, the domain controller 346 canprovide remote Internet access to IPTV account information, e-mail,personalized Internet services, or other online services via the publicnetwork 312. In addition, the second APP switch 340 can be coupled to asubscriber and system store 348 that includes account information, suchas account information that is associated with users who access the IPTVsystem 300 via the private network 310 or the public network 312. In anillustrative embodiment, the subscriber and system store 348 can storesubscriber or customer data and create subscriber or customer profilesthat are associated with IP addresses, stock-keeping unit (SKU) numbers,other identifiers, or any combination thereof, of corresponding set-topbox devices 316, 324. In another illustrative embodiment, the subscriberand system store can store data associated with capabilities of set-topbox devices associated with particular customers.

In a particular embodiment, the application tier 304 can include aclient gateway 350 that communicates data directly to the client-facingtier 302. In this embodiment, the client gateway 350 can be coupleddirectly to the CFT switch 330. The client gateway 350 can provide useraccess to the private network 310 and the tiers coupled thereto. In anillustrative embodiment, the set-top box devices 316, 324 can access theIPTV system 300 via the access network 366, using information receivedfrom the client gateway 350. User devices can access the client gateway350 via the access network 366, and the client gateway 350 can allowsuch devices to access the private network 310 once the devices areauthenticated or verified. Similarly, the client gateway 350 can preventunauthorized devices, such as hacker computers or stolen set-top boxdevices from accessing the private network 310, by denying access tothese devices beyond the access network 366.

For example, when the first representative set-top box device 316accesses the client-facing tier 302 via the access network 366, theclient gateway 350 can verify subscriber information by communicatingwith the subscriber and system store 348 via the private network 310.Further, the client gateway 350 can verify billing information andstatus by communicating with the OSS/BSS gateway 344 via the privatenetwork 310. In one embodiment, the OSS/BSS gateway 344 can transmit aquery via the public network 312 to the OSS/BSS server 364. After theclient gateway 350 confirms subscriber and/or billing information, theclient gateway 350 can allow the set-top box device 316 to access IPTVcontent and VoD content at the client-facing tier 302. If the clientgateway 350 cannot verify subscriber information for the set-top boxdevice 316, because it is connected to an unauthorized twisted pair, theclient gateway 350 can block transmissions to and from the set-top boxdevice 316 beyond the access network 366.

As indicated in FIG. 3, the acquisition tier 306 includes an acquisitiontier (AQT) switch 352 that communicates with the private network 310.The AQT switch 352 can also communicate with the operations andmanagement tier 308 via the public network 312. In a particularembodiment, the AQT switch 352 can be coupled to one or more liveAcquisition-servers (A-servers) 354 that receive or acquire televisioncontent, movie content, advertisement content, other video content, orany combination thereof, from a broadcast service 356, such as asatellite acquisition system or satellite head-end office. In aparticular embodiment, the live acquisition server 354 can transmitcontent to the AQT switch 352, and the AQT switch 352 can transmit thecontent to the CFT switch 330 via the private network 310.

In an illustrative embodiment, content can be transmitted to theD-servers 332, where it can be encoded, formatted, stored, replicated,or otherwise manipulated and prepared for communication from the videoserver(s) 380 to the set-top box devices 316, 324. The CFT switch 330can receive content from the video server(s) 380 and communicate thecontent to the CPE 314, 322 via the access network 366. The set-top boxdevices 316, 324 can receive the content via the CPE 314, 322, and cantransmit the content to the television monitors 318, 326. In anillustrative embodiment, video or audio portions of the content can bestreamed to the set-top box devices 316, 324.

Further, the AQT switch 352 can be coupled to a video-on-demand importerserver 358 that receives and stores television or movie content receivedat the acquisition tier 306 and communicates the stored content to theVoD server 336 at the client-facing tier 302 via the private network310. Additionally, at the acquisition tier 306, the VoD importer server358 can receive content from one or more VoD sources outside the IPTVsystem 300, such as movie studios and programmers of non-live content.The VoD importer server 358 can transmit the VoD content to the AQTswitch 352, and the AQT switch 352, in turn, can communicate thematerial to the CFT switch 330 via the private network 310. The VoDcontent can be stored at one or more servers, such as the VoD server336.

When users issue requests for VoD content via the set-top box devices316, 324, the requests can be transmitted over the access network 366 tothe VoD server 336, via the CFT switch 330. Upon receiving suchrequests, the VoD server 336 can retrieve the requested VoD content andtransmit the content to the set-top box devices 316, 324 across theaccess network 366, via the CFT switch 330. The set-top box devices 316,324 can transmit the VoD content to the television monitors 318, 326. Inan illustrative embodiment, video or audio portions of VoD content canbe streamed to the set-top box devices 316, 324.

FIG. 3 further illustrates that the operations and management tier 308can include an operations and management tier (OMT) switch 360 thatconducts communication between the operations and management tier 308and the public network 312. In the embodiment illustrated by FIG. 3, theOMT switch 360 is coupled to a TV2 server 362. Additionally, the OMTswitch 360 can be coupled to an OSS/BSS server 364 and to a simplenetwork management protocol monitor 386 that monitors network deviceswithin or coupled to the IPTV system 300. In a particular embodiment,the OMT switch 360 can communicate with the AQT switch 352 via thepublic network 312.

The OSS/BSS server 364 may include a cluster of servers, such as one ormore CPE data collection servers that are adapted to request and storeoperations systems data, such as performance data from the set-top boxdevices 316, 324. In an illustrative embodiment, the CPE data collectionservers may be adapted to analyze performance data to identify acondition of a physical component of a network path associated with aset-top box device, to predict a condition of a physical component of anetwork path associated with a set-top box device, or any combinationthereof.

In an illustrative embodiment, the live acquisition server 354 cantransmit content to the AQT switch 352, and the AQT switch 352, in turn,can transmit the content to the OMT switch 360 via the public network312. In this embodiment, the OMT switch 360 can transmit the content tothe TV2 server 362 for display to users accessing the user interface atthe TV2 server 362. For example, a user can access the TV2 server 362using a personal computer 368 coupled to the public network 312.

It should be apparent to one of ordinary skill in the art from theforegoing media communication system embodiments that other suitablemedia communication systems for distributing broadcast media content aswell as peer-to-peer exchange of content can be applied to the presentdisclosure.

FIG. 4 depicts an illustrative embodiment of a communication system 400employing an IP Multimedia Subsystem (IMS) network architecture.Communication system 400 can be overlaid or operably coupled withcommunication systems 100-300 as another representative embodiment ofsaid communication systems.

The communication system 400 can comprise a Home Subscriber Server (HSS)440, a tElephone NUmber Mapping (ENUM) server 430, and network elementsof an IMS network 450. The IMS network 450 can be coupled to IMScompliant communication devices (CD) 401, 402 or a Public SwitchedTelephone Network (PSTN) CD 403 using a Media Gateway Control Function(MGCF) 420 that connects the call through a common PSTN network 460.

IMS CDs 401, 402 register with the IMS network 450 by contacting a ProxyCall Session Control Function (P-CSCF) which communicates with acorresponding Serving CSCF (S-CSCF) to register the CDs with anAuthentication, Authorization and Accounting (AAA) supported by the HSS440. To accomplish a communication session between CDs, an originatingIMS CD 401 can submit a Session Initiation Protocol (SIP INVITE) messageto an originating P-CSCF 404 which communicates with a correspondingoriginating S-CSCF 406. The originating S-CSCF 406 can submit the SIPINVITE message to an application server (AS) such as reference 410 thatcan provide a variety of services to IMS subscribers. For example, theapplication server 410 can be used to perform originating treatmentfunctions on the calling party number received by the originating S-CSCF406 in the SIP INVITE message.

Originating treatment functions can include determining whether thecalling party number has international calling services, and/or isrequesting special telephony features (such as *72 forward calls, *73cancel call forwarding, *67 for caller ID blocking, and so on).Additionally, the originating S-CSCF 406 can submit queries to the ENUMsystem 430 to translate an E.164 telephone number to a SIP UniformResource Identifier (URI) if the targeted communication device is IMScompliant. If the targeted communication device is a PSTN device, theENUM system 430 will respond with an unsuccessful address resolution andthe S-CSCF 406 will forward the call to the MGCF 420 via a BreakoutGateway Control Function (BGCF) 419.

When the ENUM server 430 returns a SIP URI, the SIP URI is used by anInterrogating CSCF (I-CSCF) 407 to submit a query to the HSS 440 toidentify a terminating S-CSCF 414 associated with a terminating IMS CDsuch as reference 402. Once identified, the I-CSCF 407 can submit theSIP INVITE to the terminating S-CSCF 414 which can call on anapplication server 411 similar to reference 410 to perform theoriginating treatment telephony functions described earlier. Theterminating S-CSCF 414 can then identify a terminating P-CSCF 416associated with the terminating CD 402. The P-CSCF 416 then signals theCD 402 to establish communications. The aforementioned process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 4 can be interchanged.

FIG. 5 depicts an illustrative embodiment of a portal 530. The portal530 can be used for managing services of communication systems 100-400.The portal 530 can be accessed by a Uniform Resource Locator (URL) witha common Internet browser such as Microsoft's Internet Explorer using anInternet-capable communication device such as references 108, 116, or210 of FIGS. 1-2. The portal 530 can be configured to access a mediaprocessor such as references 106, 204, 206, 316, and 324 of FIGS. 1-3and services managed thereby such as a Digital Video Recorder (DVR), anElectronic Programming Guide (EPG), VoD catalog, a personal catalogstored in the STB (such as personal videos, pictures, audio recordings,etc.), and so on.

FIG. 6 depicts an exemplary embodiment of a communication device 600.Communication device 600 can be a representative portion of any of theaforementioned communication devices of FIGS. 1-4. The communicationdevice 604 can comprise a wireline and/or wireless transceiver 602(herein transceiver 602), a user interface (UI) 604, a power supply 614,and a controller 606 for managing operations thereof. The transceiver602 can support short-range or long-range wireless access technologiessuch as a Bluetooth wireless access protocol, a Wireless Fidelity (WiFi)access protocol, a Digital Enhanced Cordless Telecommunications (DECT)wireless access protocol, cellular, software defined radio (SDR) and/orWiMAX technologies, just to mention a few. Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,and next generation technologies as they arise.

The transceiver 602 can also support common wireline access technologiessuch as circuit-switched wireline access technologies, packet-switchedwireline access technologies, or combinations thereof. PSTN canrepresent one of the common circuit-switched wireline accesstechnologies. Voice over Internet Protocol (VoIP), and IP datacommunications can represent some of the commonly availablepacket-switched wireline access technologies. The transceiver 602 canalso be adapted to support IP Multimedia Subsystem (IMS) protocol forinterfacing to an IMS network that can combine PSTN and VoIPcommunication technologies.

The UI 604 can include a depressible or touch-sensitive keypad 608 and anavigation mechanism such as a roller ball, joystick, mouse, and/ornavigation disk for manipulating operations of the communication device600. The keypad 608 can be an integral part of a housing assembly of thecommunication device 600 or an independent device operably coupledthereto by a tethered wiring interface (such as a USB) or a wirelessinterface supporting for example Bluetooth. The keypad 608 can representa numeric dialing keypad commonly used by phones, and/or a Qwerty keypadwith alphanumeric keys.

The UI 604 can further include a display 610 such as monochrome or colorLCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) orother suitable display technology for conveying images to the end userof the communication device 600. In an embodiment where the display 610is touch-sensitive, a portion or all of the keypad 608 can be presentedby way of the display. The UI 604 can also include an audio system 612that utilizes common audio technology for conveying low volume audio(such as audio heard only in the proximity of a human ear) and highvolume audio (such as speakerphone for hands free operation). The audiosystem 612 can further include a microphone for receiving audiblesignals of an end user.

The power supply 614 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and charging system technologies for supplying energy tothe components of the communication device 600 to facilitate long-rangeor short-range portable applications. The controller 606 can utilizecomputing technologies such as a microprocessor and/or digital signalprocessor (DSP) with associated storage memory such a Flash, ROM, RAM,SRAM, DRAM or other storage technologies.

As noted above, broadcast television over IP is one service of IPTV. Toefficiently deliver such broadcast TV in the network to users, IPmulticast is used since it provides huge bandwidth efficiencies overunicast delivery. For national channels the IPTV streams are sent toevery local market, independent of whether there are currently viewersin each local market for a particular channel. This is done to improvethe channel change time latency. To accomplish this, static joins mustbe created on every edge delivery router in the network across all localmarkets. As more channels are added to the network, the stateinformation grows. When nodes are added to the network or maintenance isperformed that takes new nodes or links or when there are node or linkfailures, then the time to reroute the multicast traffic depends on theamount of multicast routing state present in the network. Furthermore,pre-positioning multicast state in every local market edge routerrequires configuring static multicast joins in every one of the localmarket edge routers. This is a very large amount of configuration and ittouches every router which can be an operational scale problem. Thescale problem can thus occur every time new channel streams are added tothe network. It is easy to miss a configuration because a node isunavailable or because of maintenance events that may remove or updateconfigurations. Such continual activity as the number of edge elementsincreases leads to configuration errors and thus loss of service in thenetwork. Such an arrangement also makes migration of the multicastdelivery architecture to updated designs or new addressing difficultbecause of the amount of configuration that must be changed.

Using a multicast VPN to delivery national broadcast IPTV can eliminatemany of the issues encountered. Multicast VPN means using a service suchas MPLS VPNs that create carrier based private networks, such as aservice AT&T offers to their enterprise customers. Such VPN services areused to provide isolation and privacy of individual networks and Qualityof Service (QoS) for the individual customers. But contrary to thetraditional goal of VPN services of providing isolation and privacy of avirtual network, the embodiments herein apply a multicast VPN service toeliminate multicast state in the backbone and eliminate the statemulticast join configuration at each egress edge router in the localrouters. Thus, embodiments herein can involve creating a multicast VPNacross the backbone network. Every edge router (that connects tomulticast clients whether caching servers or customers and to multicastsources) is treated as a provider edge (PE) router (commonly known inMPLS VPN terminology). A single VPN with a single multicast domain tree(MDT) can be created among these PE routers. In a multicast VPN, asingle private multicast group can be used to create the MDT in thebackbone, independent of the number of active external multicast groups.Further, every PE router can join this MDT without requiring knowledgeof whether there are receivers for the multicast groups carried in theVPN. In a normal multicast VPN, the MDT creates inefficiencies bytransmitting multicast packets to PE routers that may not have anyreceivers. However, for the broadcast IPTV application, every PE routerrequires that every channel be received, but such a system can eliminatethe need to created static joins for each external multicast group onthe PE router. Since only a single group is present in the backbone ofthe network, route state stays constant and convergence time is optimal.Furthermore, there is only a single VPN in the private IPTV backboneapplication. There are no other multicast VPNs that might contribute tostate growth in this network as might be present in a retail VPN servicewith very large numbers and growth of customers.

Convergence for the national broadcast IPTV is constant in such anetwork since the multicast state is constant since only a single groupis present. Also the only static multicast joins needed in the networkare at the ingress PE routers where the sources are connected. No staticjoins are needed at the egress PE routers where the receivers areattached. Again, a problem that grows without bound and is a challengeoperationally to maintain is substituted with a configuration where asingle or bounded number of ingress PE routers exists.

FIG. 7 depicts an illustrative method 700 operating in portions ofcommunication systems 100-400. Method 700 begins with step 702 in whichdelivery of national broadcast IPTV uses national multicast VPNs todeliver national broadcast channels by way of IPTV edge routers using anMPLS protocol and at 704 shares a same multicast state and shares a samemulticast delivery tree for the national broadcast channels. At 706, themethod can use MPLS VPNs that create carrier based private networks. Themethod can apply multicast VPN service to eliminate multicast stateinformation in a backbone of a network and to eliminate state multicastjoin configuration information at each egress edge router in localrouters at 708. The method 700 at 710 in this regard creates a multicastVPN across a backbone network. At 712, the method treats every edgerouter as a provider edge (PE) router where a single VPN with a singlemulticast domain tree (MDT) is created among the PE routers whicheliminates static joins for each external multicast group on the PE. At714, the PE routers can joint the MDT without requiring knowledge ofwhether there are receivers for the multicast groups carried in the VPN.At 716, the multicast state remains constant due to having a singlemulticast group. Thus, only static multicast joins are used in thenetwork at ingress PE routers.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope andspirit of the claims described below. For example, VPNs other than MPLSVPNs can comprise the network or networks as contemplated herein.

Other suitable modifications can be applied to the present disclosurewithout departing from the scope of the claims below. Accordingly, thereader is directed to the claims section for a fuller understanding ofthe breadth and scope of the present disclosure.

FIG. 8 depicts an illustrative diagrammatic representation of a machinein the form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethodologies discussed above. In some embodiments, the machine operatesas a standalone device. In some embodiments, the machine may beconnected (using a network) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a laptop computer, a desktopcomputer, a control system, a network router, switch or bridge, or anymachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a device of the present disclosure includes broadly anyelectronic device that provides voice, video or data communication.Further, while a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The computer system 800 may include a processor 802 (such as a centralprocessing unit (CPU)), a graphics processing unit (GPU, or both), amain memory 804 and a static memory 806, which communicate with eachother via a bus 808. The computer system 800 may further include a videodisplay unit 810 (such as a liquid crystal display (LCD)), a flat panel,a solid state display, or a cathode ray tube (CRT)). The computer system800 may include an input device 812 (such as a keyboard), a cursorcontrol device 814 (such as a mouse), a disk drive unit 816, a signalgeneration device 818 (such as a speaker or remote control) and anetwork interface device 820.

The disk drive unit 816 may include a computer-readable medium 822 onwhich is stored one or more sets of instructions (such as software 824)embodying any one or more of the methodologies or functions describedherein, including those methods illustrated above. The instructions 824may also reside, completely or at least partially, within the mainmemory 804, the static memory 806, and/or within the processor 802during execution thereof by the computer system 800. The main memory 804and the processor 802 also may constitute computer-readable media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Applications that may include the apparatusand systems of various embodiments broadly include a variety ofelectronic and computer systems. Some embodiments implement functions intwo or more specific interconnected hardware modules or devices withrelated control and data signals communicated between and through themodules, or as portions of an application-specific integrated circuit.Thus, the example system is applicable to software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, or virtualmachine processing can also be constructed to implement the methodsdescribed herein.

The present disclosure contemplates a machine readable medium containinginstructions 824, or that which receives and executes instructions 824from a propagated signal so that a device connected to a networkenvironment 826 can send or receive voice, video or data, and tocommunicate over the network 826 using the instructions 824. Theinstructions 824 may further be transmitted or received over a network826 via the network interface device 820.

While the computer-readable medium 822 is shown in an example embodimentto be a single medium, the term “computer-readable medium” should betaken to include a single medium or multiple media (such as acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“computer-readable medium” shall also be taken to include any mediumthat is capable of storing, encoding or carrying a set of instructionsfor execution by the machine and that cause the machine to perform anyone or more of the methodologies of the present disclosure.

The term “computer-readable medium” shall accordingly be taken toinclude, but not be limited to: solid-state memories such as a memorycard or other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories; magneto-optical or optical medium such as a disk or tape;and/or a digital file attachment to e-mail or other self-containedinformation archive or set of archives is considered a distributionmedium equivalent to a tangible storage medium. Accordingly, thedisclosure is considered to include any one or more of acomputer-readable medium or a distribution medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (such as TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are periodicallysuperseded by faster or more efficient equivalents having essentiallythe same functions. Accordingly, replacement standards and protocolshaving the same functions are considered equivalents.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are also merely representationaland may not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in a single embodiment for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A method, comprising: providing, by a systemcomprising a processor, a first group of routers of a media system withstatic multicast join configuration information without providing asecond group of routers of the media system with the static multicastjoin configuration information; delivering, by the system, nationalbroadcast channels via a multicast virtual private network, wherein themulticast virtual private network utilizes the first and second groupsof routers to deliver the national broadcast channels; sharing, by thesystem, a same multicast state and a same multicast delivery tree forthe national broadcast channels; and maintaining, by the system, astatic number of the first group of routers for the multicast virtualprivate network.
 2. The method of claim 1, wherein the second group ofrouters includes only egress edge routers, and wherein the sharing ofthe same multicast state and the same multicast delivery tree isperformed by transmitting multicast data via a multi-protocol labelswitching protocol to selected network elements.
 3. The method of claim2, wherein the first group of routers includes only ingress edgerouters, and wherein the multicast virtual private network furtherutilizes the multi protocol label switching protocol to deliver thenational broadcast channels.
 4. The method of claim 1, wherein thesecond group of routers join a multicast domain tree without receivinginformation indicating whether there are receivers for multicast groupscarried in the multicast virtual private network, and wherein thesharing of the same multicast state and the same multicast delivery treeis performed by transmitting multicast data via a multi-protocol labelswitching protocol to selected network elements.
 5. The method of claim1, wherein the delivering of the national broadcast channels isperformed by creating a single multicast domain tree among the first andsecond groups of routers.
 6. The method of claim 5, wherein the secondgroup of routers join the multicast domain tree without receivinginformation indicating whether there are receivers for multicast groupscarried in the multicast virtual private network.
 7. A machine-readablestorage device, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprising:delivering broadcast channels using a multicast virtual private network,wherein the multicast virtual private network utilizes a first group ofnetworking devices provisioned with static multicast join configurationinformation, and wherein the multicast virtual private network utilizesa second group of networking devices that are provisioned without thestatic multicast join configuration information; and applying amulti-protocol label switching protocol to the multicast virtual privatenetwork to share a same multicast state for the broadcast channels. 8.The machine-readable storage device of claim 7, wherein the operationsfurther comprise maintaining a static number of the first group ofnetworking devices for the multicast virtual private network.
 9. Themachine-readable storage device of claim 7, wherein the operationsfurther comprise generating a single multicast domain tree among thefirst and second groups of networking devices.
 10. The machine-readablestorage device of claim 7, wherein the second group of networkingdevices includes only egress edge networking devices.
 11. Themachine-readable storage device of claim 7, wherein the second group ofnetworking devices join a multicast domain tree without receivinginformation indicating whether there are receivers for multicast groupscarried in the multicast virtual private network, and wherein thesharing of the multicast state is performed by transmitting multicastdata via a multi-protocol label switching protocol to selected networkelements.
 12. The machine-readable storage device of claim 7, whereinthe first and second groups of networking devices are edge networkingdevices.
 13. The machine-readable storage device of claim 12, whereinthe edge networking devices include provider edge networking devices andcustomer edge networking devices, and wherein a single multicast domaintree is created among the edge networking devices.
 14. Themachine-readable storage device of claim 13, wherein egress edgenetworking devices of the second group of networking devices join thesingle multicast domain tree without receiving information indicatingwhether there are receivers for multicast groups carried in themulticast virtual private network.
 15. The machine-readable storagedevice of claim 7, wherein only static multicast joins are used in themulticast virtual private network at the first group of networkingdevices.
 16. A system, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, comprising: delivering broadcast contentusing a multicast virtual private network, wherein the multicast virtualprivate network utilizes a first group of network elements provisionedwith static multicast join configuration information, and wherein themulticast virtual private network utilizes a second group of networkelements that are provisioned without the static multicast joinconfiguration information; and applying a multi-protocol label switchingprotocol to the multicast virtual private network to share a samemulticast state for the broadcast content.
 17. The system of claim 16,wherein the operations further comprise: sharing a same multicast statefor the broadcast content; and sharing a same multicast delivery treefor the broadcast content, and wherein the broadcast content isdelivered by one of an internet protocol television communicationsystem, a cable television communication system, or a satellitetelevision communication system.
 18. The system of claim 16, wherein thesecond group of network elements includes only egress edge networkelements, and wherein the first group of network elements includes onlyingress edge network elements.
 19. The system of claim 16, wherein thesecond group of network elements join a multicast domain tree withoutreceiving information indicating whether there are receivers formulticast groups carried in the multicast virtual private network, andwherein the sharing of the multicast state is performed by transmittingmulticast data via a multi-protocol label switching protocol to selectednetwork elements.
 20. The system of claim 16, wherein the operationsfurther comprise maintaining a static number of the first group ofnetwork elements for the multicast virtual private network, and whereinonly static multicast joins are used in the multicast virtual privatenetwork at the first group of network elements.